Hi Team, I am using Rational DOORS 9.6.1.10. I received a DXL popup error with incorrect path "<\\XXXXX\addins$\XXXX\include\checkModName." when closing a module.
I am able to find this is because a module trigger.
Name of trigger: OnFModuleExit
Please help me find the trigger script, as I need to know which task it is trying to perform on module exit. Kindly help me with a DXL to edit / delete the trigger.
Regards, Sousan
sousan - Tue Apr 16 03:35:31 EDT 2019 |
Re: Module trigger has inaccessible path Hi Sousan,
Basically the path on the trigger for the include is incorrect from #include <\\XXXXX\addins$\XXXX\include\checkModName> to #include <//XXXXX/addins$/XXXX/include/checkModName> Otherwise use "" for string and escape \
Costas
|
Re: Module trigger has inaccessible path Hi Costas, Thank you for your answer. Could you please help me with the steps to check where exactly the trigger is located and edit the path in it.
Regards, Sousan |
Re: Module trigger has inaccessible path sousan - Tue Apr 16 04:58:23 EDT 2019 Hi Costas, Thank you for your answer. Could you please help me with the steps to check where exactly the trigger is located and edit the path in it.
Regards, Sousan Triggers are stored in modules, projects or in the database. You can find trigger by using the loops for trigger in module, for trigger in project or for trigger in database loop. When you get hold of a trigger you can examine it, for example by retrieving the trigger dxl code. Here is a example snippet:
Module m = current
Trigger t
for t in m do
{
print stringOf(level t) "\n"
print stringOf(type t) "\n"
print stringOf(event t) "\n"
print priority(t) "\n"
print dxl(t) "\n"
}
Manipulating the dxl code is not as straightforward as you may think. You need to delete the trigger and recreate it. If you have the original code that would be the way to go. If not, there is more work to do. You need to collect all information about the trigger that is needed to recreate it, including the "trigger level assembly". I suggest you have a look in Trigger chapter of the DXL reference manual. I apologize if I have made this more complicated than it is. If so, I hope someone can point out a simpler solution. |
Re: Module trigger has inaccessible path Hi Sousan, as Henrik pointed out, it may be quite difficult to modify the code after the trigger is installed. I wonder whether it is easier to find the person who installed the trigger. You mention the line #include <\\XXXXX\addins$\YYYYY\include\checkModName> Given this, I assume that YYYYY is an add-on to DOORS, part of an extension for some functionality. Usually there is a person in your company that has the responsibility to maintain this extension. And I'm sure this person has a rollout script for the extension for the case that the server name (XXXXX) has changed. I bet that there are lots of modules in your database that have this problem and that there is more than one trigger involved. The DOORS administration team in your company should be able to help you.
And may be it is simply a matter of access rights. As soon as your account has read access rights to the hidden share \\XXXXX\addin$, your module should close without any problems.
Regards,
|
Re: Module trigger has inaccessible path Without a doubt, each desired Trigger should have code that deploys and removes it. In your case, though, you need to find an existing trigger and remove it. You won't be able to write AI to find and fix code in an existing trigger. I think that in morastor's code, you can decide if you want to delete it then "delete(t); save(m)". I would retrieve the "kind(t)" of trigger and only proceed if it is "stored" (ignoring "dyanamic" and "builtin"). You will probably want the trigger's "name(t)". But this error highlights the relative disaster of using #include statements in Attr-DXL, Layouts, and Triggers. If the module is used by someone who is somewhere else or otherwise doesn't have access, that person will get these errors. -Louie |
Re: Module trigger has inaccessible path Thank you All, I removed the trigger from database to fix the issue.
Regards, Sousan
|